This adds a new method, extendIntegration, that can be used to safely extend an integration.

Today, we have the problem that if we extend an integration (e.g. node extending something from server-utils), we have to manually call the parent integration functions. This is a bit brittle because a) it requires you to know exactly what methods the parent integration has, which we usually want to abstract away from users on purpose. also, if a parent integration changes, this could be forgotten/lost.

Usage:

const _denoMysqlIntegration = (() => {
  const inner = mysqlChannelIntegration();

  return extendIntegration(inner, {
    name: INTEGRATION_NAME,
    setupOnce() {
      setAsyncLocalStorageAsyncContextStrategy();
    },
  });
}) satisfies IntegrationFn;

vs. before:

onst _denoMysqlIntegration = (() => {
  const inner = mysqlChannelIntegration();
  return {
    name: INTEGRATION_NAME,
    setupOnce() {
      setAsyncLocalStorageAsyncContextStrategy();
      inner.setupOnce?.();
    },
  };
}) satisfies IntegrationFn;

In addition, I also improved defineIntegration to maintain a static name, and made all integration names static for easier access.

Note: We have a bunch of places where we started to type integrations manually, e.g.

export const denoMysqlIntegration = defineIntegration(_denoMysqlIntegration) as () => Integration & {
  name: 'DenoMysql';
  setupOnce: () => void;
};

We should revert this in v11. We purposefully did not do this because we want to keep the underlying implementation flexible. I think this was done sometimes to make it easier to extend/call things, but usually this should not be necessary and the extend helper should help with making things type safe a bit easier.